Repository navigation
chore: bump internal dependency ranges to the latest published patch versions - #70
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Points each consumer's internal dependency range at the latest published patch:
@kiritan/deepl,@kiritan/free-translate,@kiritan/google-translate:@kiritan/middleware^0.1.0→^0.1.1kiritan:@kiritan/runtime^0.2.0→^0.2.1^0.1.0/^0.2.0already matched the newer patch releases (0.x caret ranges), so this changes nothing at resolution time for anyone already on the latest — it just keeps the declared minimum honest. Will be followed by a patch release of each of these four packages.Why?
Requested: after bumping
@kiritan/middleware/@kiritan/runtime, keep the packages that depend on them pointed at the latest patch, and re-release.Related issue(s)
closes
Check
CONTRIBUTING.md(rules)npm run check(lint & format)npm run typechecknpm run test(functions test)npm run build(dist/)npm run test:coverageand check nothing new went uncovered